2020-06 Release Notes
Iteration: 2020-06
June 01, 2020
What’s New?
| 3697 | Show the Payment Subscriber Id in the Enrollment Details screen. |
| 3697 | Hide the second commodity information on Rates Wizard summary screen if only one has been selected by the user. |
| 3719 | Added the new datamart extract Account Exemptions. |
| 3143 | Allow to store multiple payment methods in OpsAdmin. |
| 3737 | Opsadmin can now download datamarts from ESG database besides FTP files. |
Fixes and Improvements
| 3743 | Some replacement values were showing information of the incorrect brand. |
| 3746 | OpsAdmin was wrongly submitting enrollments to ESG with some autopay fields when the process was made from the Enrollments Manager. |
| 3143 | Issue that allowed enrollment without enabling recurring billing when no deposit was required. |
| 3665 | Drops were being imported associated with an old LDC. |
| 3728 | When submitting a prospect to the billing system, a red empty error box was shown. |
| 3724 | Regression where the search button wasn’t showing with reduced filters in Customer Support. |
| ¯\_(ツ)_/¯ | Transfer Of Service now migrates recurring billing information if the new enrollment is generated automatically. |
| ¯\_(ツ)_/¯ | Background Services Status was showing as failed, tasks that actually finished successfully. |
| ¯\_(ツ)_/¯ | Role Group screen only shows roles associated with the enabled OpsAdmin modules. |
| ¯\_(ツ)_/¯ | When the customer logged in the rates wizard and advanced to the following steps, the system was showing a message saying the password was incorrect. |
| ¯\_(ツ)_/¯ | Now it’s possible to paste on the Plan and Enrollment fields in the Log History screen. |
| ¯\_(ツ)_/¯ | Recurring billing data was being marked as Sent To ESG when the submit process failed. |
| ¯\_(ツ)_/¯ | In Quick Enrollments, if the user gets to the customer step, goes back, and returns to the customer step, some credit check fields were shown incorrectly. |
| ¯\_(ツ)_/¯ | It wasn’t possible to upload big files for Customer Look-Up. |
| 3740 | Improved validation and error message when importing accounts for utilities that require zone |
| 3697, 3605 | UI changes to better explain some Brand Configuration fields. |
| 3708 | Now the Letter Of Credit upload screen only shows and allows to select PDF files. |
| 3697 | Removed On Hold - Credit Check Pending because it’s no longer used. |
| 3670 | Several new validations to prevent error when a plan is saved. |
| ¯\_(ツ)_/¯ | Better error message when submitting enrollments to the billing system from the Enrollments Manager. |
| ¯\_(ツ)_/¯ | When the customer enrolls in the Texas Market, the system now shows a Processing message when validating the ESIID and address selected. |
Features & Fixes Details
Show the Payment Subscriber Id in the Enrollment Details screen
A new panel is available in the Enrollment Details view that will show the subscriber Id that will be used by ESG to process the recurring billing. This information is only visible for markets that have payments enabled.
If the Id is presented here, but not visible in ESG, it means that the payment information was generated in Authorize.Net but failed to be sent to ESG. If there is no payment subscriber Id it means that the customer chose not to enable recurring billing (currently not possible) or that the enrollment process failed to send the information to Authorize.Net.
Added the new datamart extract Account Exemptions
Now it’s possible to enable the account exemptions datamart import from ESG. To enable it please contact Stormcrest support.
Allow to store multiple payment methods in OpsAdmin
ESG has a serious limitation in it’s integration with Authorize.Net and is that it only uses the customer id generated by Authorize.Net to generate payments, instead of also using the payment method id. This means that only a single credit card can be stored per customer, or if multiple credit cards are stored in Authorize.Net, one has to be set as the default one or the process will fail.
To workaround this limitation, OpsAdmin uses that same default functionality as a way to allow multiple payment methods per customer although no interaction from the user is required, everything is automatically handled by the system.
When a new customer enrolls and is requested to add a payment method for autopay, that method will be automatically marked as the default one. If a returning customer is the one enrolling and already has a payment method being used for recurring billing in other enrollment, then that payment method will be listed and it will be the only option to select for recurring billing. This happens because only a single payment method can be selected as the default one in Authorize.Net and because of that, the same has to be used for all the enrollments.
From My Account, the customer will be able to change the payment method used for recurring billing, which internally will change the default designation. The limitation of this, is that it will affect all enrollments. Also, the change will take effect immediately, and the customer won’t be able to select a different date for the change to take effect. This last feature is already built into OpsAdmin but will remain disabled until this workaround is removed once ESG adapts their system.
Opsadmin can now download datamarts from ESG database besides FTP files
Now OpsAdmin allows to import the datamart information from ESG databases instead of using the FTP files. The process is basically the same. It just changes the source of the information. Nevertheless, there are two things to consider:
- This change has to be requested to ESG by each company before making the change in OpsAdmin.
- The Service Agreement Extract will keep being updated using the FTP as it is still not available on ESG databases as of the time of writing this release notes.
UI changes to better explain some Brand Configuration fields
We added some extra information to help the user configure the different brands.
First there is an indication in the Branding Name field warning that changing this with an incorrect value could break the validation made by P2C. And second, a small reminder that the variable [STATE] exists for the message shown to the customer when the zip code entered corresponds to a different brand.
